Committed to connecting the world

  •  
wtisd

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : G.9903 (2012) Amd.1     
  ITU-T A.5 justification information for referenced document IETF RFC 5444 (2009) in draft G.9903 (2012) Amd.1
1. Clear description of the referenced document:
Name: IETF RFC 5444 (2009)
Title: Generalized Mobile Ad Hoc Network (MANET) Packet/Message Format
2. Status of approval:
RFC - Proposed Standard (IETF Stream)
3. Justification for the specific reference:
The routing protocol uses control messages as in RFC 5444.
4. Current information, if any, about IPR issues:
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=5444
5. Other useful information describing the "Quality" of the document:
The status of the referred RFC, is "Proposed Standard".
6. The degree of stability or maturity of the document:
The status of the referred RFC, is "Proposed Standard".
7. Relationship with other existing or emerging documents:
8. Any explicit references within that referenced document should also be listed:
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", RFC 2119, BCP 14, March 1997./
/
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing/
Architecture", RFC 4291, February 2006./
/
[BCP26] Narten, T. and H. Alvestrand, "Guidelines for Writing/
an IANA Considerations Section in RFCs", BCP 26,/
RFC 5226, May 2008./
/
[SingleUNIX] IEEE Std 1003.1, The Open Group, and ISO/IEC JTC/
1/SC22/WG15, "Single UNIX Specification, Version 3,/
2004 Edition", April 2004./
9. Qualification of ISOC/IETF:
9.1-9.6     Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7     The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8     Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
10. Other (for any supplementary information):
None
Note: This form is based on Recommendation ITU-T A.5